failure 200:
Requirement failed: {tgetnum.05.02} return ERR
| location |
| trace |
/var/opt/lsb/test/olver-core/2013-01-18_15-48-05/ncurses_terminal_termcap_simple_scenario.utz (ncurses_terminal_termcap_simple_scenario.utt), line 249 |
| occurence |
| scenario |
ncurses_terminal_termcap_simple_scenario |
| specification function |
tgetnum_spec() |
| parameter value |
CallContext context = [pid=3755,thr=b74346c0] |
| parameter value |
CString * @id = li |
| parameter value |
CString * id = li |
| return value |
(IntT) 25 |
coverage
& branch |
pseudo_coverage
The only branch |
| properties |
| REQ failed |
tgetnum.05.02 |
| kind |
POSTCONDITION_FAILED |
similar known bug(s)
|
According to the standard, upon successful completion, tgetnum() function from Ncurses
library shall return OK(0), otherwise, it shall return ERR(-1).
RETURN VALUE
...
Upon successful completion, functions that return an integer return OK.
Otherwise, they return ERR.
But the real implementation does not match LSB standard.
Manual pages for GNU extension, that is used in real Linux systems, say:
The tgetnum routine gets the numeric entry for id, or -1 if it is not available.
Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0686.
|
|